Skip to content

chore: Update read environment variables guide update with new .env guidance - #6182

Merged
bmuenzenmeyer merged 4 commits into
nodejs:mainfrom
nikhilbhatt:update-read-env-guide-with-latest-changes
Dec 12, 2023
Merged

chore: Update read environment variables guide update with new .env guidance#6182
bmuenzenmeyer merged 4 commits into
nodejs:mainfrom
nikhilbhatt:update-read-env-guide-with-latest-changes

Conversation

@nikhilbhatt

@nikhilbhatt nikhilbhatt commented Dec 11, 2023

Copy link
Copy Markdown
Contributor

Description

Fixes #6140

Validation

Related Issues

Check List

  • I have read the Contributing Guidelines and made commit messages that follow the guideline.
  • I have run npx turbo lint to ensure the code follows the style guide. And run npx turbo lint:fix to fix the style errors if necessary.
  • I have run npx turbo format to ensure the code follows the style guide.
  • I have run npx turbo test to check if all tests are passing.
  • NA I've covered new added functionality with unit tests if necessary.

@nikhilbhatt
nikhilbhatt requested a review from a team as a code owner December 11, 2023 17:51
@vercel

vercel Bot commented Dec 11, 2023

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
nodejs-org ✅ Ready (Inspect) Visit Preview 💬 Add feedback Dec 12, 2023 10:35pm

@nikhilbhatt
nikhilbhatt force-pushed the update-read-env-guide-with-latest-changes branch from 74b0687 to f7fe743 Compare December 11, 2023 18:02
@nikhilbhatt nikhilbhatt changed the title [UPDATE] Read environment variables guide update with new .env guidance chore: Update read environment variables guide update with new .env guidance Dec 11, 2023
@ovflowd ovflowd added the github_actions:pull-request Trigger Pull Request Checks label Dec 11, 2023
@github-actions github-actions Bot removed the github_actions:pull-request Trigger Pull Request Checks label Dec 11, 2023
@github-actions

github-actions Bot commented Dec 11, 2023

Copy link
Copy Markdown
Contributor

Lighthouse Results

URL Performance Accessibility Best Practices SEO Report
/en 🟢 100 🟢 97 🟢 92 🟢 92 🔗
/en/about 🟢 100 🟢 95 🟢 92 🟢 92 🔗
/en/about/previous-releases 🟢 100 🟢 93 🟢 92 🟢 92 🔗
/en/download 🟢 100 🟢 95 🟢 92 🟢 92 🔗
/en/blog 🟢 100 🟢 95 🟢 92 🟢 92 🔗

@github-actions

github-actions Bot commented Dec 11, 2023

Copy link
Copy Markdown
Contributor

Unit Test Coverage Report

Lines Statements Branches Functions
Coverage: 91%
86.91% (392/451) 73.04% (103/141) 80.45% (70/87)

Unit Test Report

Tests Skipped Failures Errors Time
71 0 💤 0 ❌ 0 🔥 4.167s ⏱️

@AugustinMauroy

Copy link
Copy Markdown
Member

Personally, I would have removed the part that talks about the dotenv package.

@AugustinMauroy AugustinMauroy left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM !!!
🎉 thanks for your first contribution !!

Comment thread pages/en/learn/command-line/how-to-read-environment-variables-from-nodejs.md Outdated
Comment thread pages/en/learn/command-line/how-to-read-environment-variables-from-nodejs.md Outdated
Signed-off-by: Brian Muenzenmeyer <brian.muenzenmeyer@gmail.com>
Merged via the queue into nodejs:main with commit e802dfb Dec 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Update how-to-read-environment-variables-from-nodejs.md with new .env guidance

5 participants